-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
invocation: rephrase slightly the proof rules to be less confusing down the line #93
Conversation
32b6444
to
80c2d60
Compare
- for invocation, reorder the parameters for a more "natural language" mental model - for delegation, make "subject" a required parameter to avoid make powerline by mistake - for delegation, implement powerline
close #75 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this actually closes #75.
// using the public key associated with the private key sent as the first | ||
// parameter. | ||
func New(iss, aud did.DID, cmd command.Command, pol policy.Policy, opts ...Option) (*Token, error) { | ||
// You can read it as "(issuer) allows (audience) to perform (cmd+pol) on (subject)". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Glad you included these - I was thinking overnight that we could also state these in "user story" form. Perhaps something like "As an Issuer, I want to allow my Audience to Invoke Command+Policy on Subject". I tried to be consistent with https://github.com/ucan-wg/spec?tab=readme-ov-file#roles.
No description provided.